Context-based cloud security assurance system

ABSTRACT

A cloud infrastructure is enhanced to provide a context-based security assurance service to enable secure application deployment. The service inspects network and cloud topologies to identify potential security capabilities and needs. Preferably, these options are then surfaced to the user with easy-to-understand, pre-configured templates representing security assurance levels. When a template (e.g., representing a pre-configured assurance level) is selected by the user, the system then applies specific capabilities and controls to translate the user-selected generalized specification (e.g., “high security”) into granular requirements for a specific set of security resources. Preferably, the identification of these security resources is based on system configuration, administration, and information associated with the pre-configured template.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is related to the following applications:

“Deployment using a context-based cloud security assurance system,” Ser.No. 14/555,741, filed Nov. 28, 2014;

“Cost-based configuration using a context-based cloud security assurancesystem,” Ser. No. 14/555,745, filed Nov. 28, 2014; and

“Administration of a context-based cloud security assurance system,”Ser. No. 14/555,748, filed Nov. 28, 2014.

BACKGROUND OF THE INVENTION

Technical Field

This disclosure relates generally to deploying applications in a “cloud”compute environment.

Background of the Related Art

An emerging information technology (IT) delivery model is cloudcomputing, by which shared resources, software and information areprovided over the Internet to computers and other devices on-demand.Cloud computing can significantly reduce IT costs and complexities whileimproving workload optimization and service delivery. With thisapproach, an application instance can be hosted and made available fromInternet-based resources that are accessible through a conventional Webbrowser over HTTP. An example application might be one that provides acommon set of messaging functions, such as email, calendaring, contactmanagement, and instant messaging. A user would then access the servicedirectly over the Internet. Using this service, an enterprise wouldplace its email, calendar and/or collaboration infrastructure in thecloud, and an end user would use an appropriate client to access his orher email, or perform a calendar operation.

Cloud compute resources are typically housed in large server farms thatrun one or more network applications, typically using a virtualizedarchitecture wherein applications run inside virtual servers, orso-called “virtual machines” (VMs), that are mapped onto physicalservers in a data center facility. The virtual machines typically run ontop of a hypervisor, which is a control program that allocates physicalresources to the virtual machines.

It is known in the art to provide appliance-based or platform-basedsolutions to facilitate rapid adoption and deployment of cloud-basedofferings. Typically, a cloud-based offering is deployed as a cloudapplication package. One such appliance that may be used for thispurpose is IBM® Workload Deployer, which is based on the IBM DataPower®7199/9005 product family. Typically, the appliance is positioneddirectly between the business workloads that many organizations use andthe underlying cloud infrastructure and platform components.Alternatively, cloud application packages may be deployed usingplatform-as-a-service (PAS) infrastructure, such as the IBM® SmartCloud®Orchestrator open cloud management platform. A management platform ofthis type typically comprises several layers including an infrastructureservices layer for provisioning, configuring and managing storage,compute and network resources, a platform services layer, and anorchestration services layer to provide business process management. Theplatform services layer includes virtual machine image lifecyclemanagement capabilities and pattern services, wherein a “pattern”provides deployment and management instructions for the businessservice. A pattern preferably is an XML-based definition of aninfrastructure configuration required to provision and managed thevarious resources (e.g., compute, networking, storage, OS, middleware,and the like) for a specific application (or application-type) workload.

As security software deployments become increasingly complex,application developers are further removed from the inner workings ofthe security environment. As a consequence, security operations oftenare left to the security experts. The move to virtualization and privateclouds, however, empowers application developers with more and moreoperational capability. Application developers then find themselves in adifficult position. In particular, when putting an application intoproduction, the developer may not have the necessary background andcontext to evaluate properly the security impact and needs of his or herapplication. Today, application developers often work with securityexperts to design a strategy for secure application deployment. Thesecurity expert, however, may encounter the same problem, but from theother direction. As applications and middleware become increasinglycomplex and virtualized, the security expert may not fully understandthe application to properly evaluate its security impact and needs.

Thus, there is a need to bridge this knowledge gap between applicationdevelopers and security experts, and to facilitate the seamless andreliable deployment of new cloud-based applications.

BRIEF SUMMARY

According to this disclosure, a cloud infrastructure is enhanced toprovide a “context-based security assurance” service to enable secureapplication deployment, e.g., by application developers, withoutrequiring such individuals to possess deep security skills or detailedunderstanding of the underlying security mechanisms upon which theirapplications may execute. Generally, the assurance service operates inassociation with a cloud application platform that includes anapplication deployment mechanism. The service inspects network and cloudtopologies to identify potential security capabilities and needs (e.g.,virtualized DMZ, IPS, resource isolation, etc.). Preferably, theseoptions are then surfaced to the user with easy-to-understand,pre-configured templates representing security assurance levels. When atemplate (e.g., representing a pre-configured assurance level) isselected by the user, the system then applies specific capabilities andcontrols to translate the user-selected generalized specification (e.g.,“high security”) into granular requirements for a specific set ofsecurity resources. Preferably, the identification of these securityresources is based on system configuration, administration, andinformation associated with the pre-configured template. Typically, thesecurity resources implemented (with respect to a particular solutionselected by the user) increase by assurance level.

Thus, based on the selected template(s), and preferably duringapplication deployment, a set of security configuration changes areapplied to an existing application execution environment to generate a“context-based” secure cloud application “zone.” Once this cloudapplication zone is defined, the application deployment is completed,and the zone provides an active protection for the application. Thisapplication zone active protection is security-context specific but, asnoted above, the approach does not require that the individual deployingthe application have detailed knowledge of the underlying securityinfrastructure.

The foregoing has outlined some of the more pertinent features of thedisclosed subject matter. These features should be construed to bemerely illustrative. Many other beneficial results can be attained byapplying the disclosed subject matter in a different manner or bymodifying the invention as will be described.

BRIEF DESCRIPTION OF THE DRAWINGS

For a more complete understanding of the present invention and theadvantages thereof, reference is now made to the following descriptionstaken in conjunction with the accompanying drawings, in which:

FIG. 1 depicts an exemplary block diagram of a distributed dataprocessing environment in which exemplary aspects of the illustrativeembodiments may be implemented;

FIG. 2 is an exemplary block diagram of a data processing system inwhich exemplary aspects of the illustrative embodiments may beimplemented;

FIG. 3 illustrates an exemplary cloud computing architecture in whichthe disclosed subject matter may be implemented;

FIG. 4 illustrates an exemplary operating environment in which anetwork-based appliance may be used to facilitate deployment of one ormore cloud-based offerings;

FIG. 5 illustrative representative functional components of thenetwork-based appliance;

FIG. 6 illustrates a block diagram of the basic operational componentsof the security assurance service of this disclosure;

FIG. 7 illustrates a representative display page of the securitymanagement interface component of the security assurance service;

FIG. 8 illustrates how the security assurance service may be used inassociation with a cloud application platform to facilitate the creationof a context-based security cloud application zone according to thisdisclosure.

DETAILED DESCRIPTION OF AN ILLUSTRATIVE EMBODIMENT

With reference now to the drawings and in particular with reference toFIGS. 1-2, exemplary diagrams of data processing environments areprovided in which illustrative embodiments of the disclosure may beimplemented. It should be appreciated that FIGS. 1-2 are only exemplaryand are not intended to assert or imply any limitation with regard tothe environments in which aspects or embodiments of the disclosedsubject matter may be implemented. Many modifications to the depictedenvironments may be made without departing from the spirit and scope ofthe present invention.

Client-Server Technologies

With reference now to the drawings, FIG. 1 depicts a pictorialrepresentation of an exemplary distributed data processing system inwhich aspects of the illustrative embodiments may be implemented.Distributed data processing system 100 may include a network ofcomputers in which aspects of the illustrative embodiments may beimplemented. The distributed data processing system 100 contains atleast one network 102, which is the medium used to provide communicationlinks between various devices and computers connected together withindistributed data processing system 100. The network 102 may includeconnections, such as wire, wireless communication links, or fiber opticcables.

In the depicted example, server 104 and server 106 are connected tonetwork 102 along with storage unit 108. In addition, clients 110, 112,and 114 are also connected to network 102. These clients 110, 112, and114 may be, for example, personal computers, network computers, or thelike. In the depicted example, server 104 provides data, such as bootfiles, operating system images, and applications to the clients 110,112, and 114. Clients 110, 112, and 114 are clients to server 104 in thedepicted example. Distributed data processing system 100 may includeadditional servers, clients, and other devices not shown.

In the depicted example, distributed data processing system 100 is theInternet with network 102 representing a worldwide collection ofnetworks and gateways that use the Transmission ControlProtocol/Internet Protocol (TCP/IP) suite of protocols to communicatewith one another. At the heart of the Internet is a backbone ofhigh-speed data communication lines between major nodes or hostcomputers, consisting of thousands of commercial, governmental,educational and other computer systems that route data and messages. Ofcourse, the distributed data processing system 100 may also beimplemented to include a number of different types of networks, such asfor example, an intranet, a local area network (LAN), a wide areanetwork (WAN), or the like. As stated above, FIG. 1 is intended as anexample, not as an architectural limitation for different embodiments ofthe disclosed subject matter, and therefore, the particular elementsshown in FIG. 1 should not be considered limiting with regard to theenvironments in which the illustrative embodiments of the presentinvention may be implemented.

With reference now to FIG. 2, a block diagram of an exemplary dataprocessing system is shown in which aspects of the illustrativeembodiments may be implemented. Data processing system 200 is an exampleof a computer, such as client 110 in FIG. 1, in which computer usablecode or instructions implementing the processes for illustrativeembodiments of the disclosure may be located.

With reference now to FIG. 2, a block diagram of a data processingsystem is shown in which illustrative embodiments may be implemented.Data processing system 200 is an example of a computer, such as server104 or client 110 in FIG. 1, in which computer-usable program code orinstructions implementing the processes may be located for theillustrative embodiments. In this illustrative example, data processingsystem 200 includes communications fabric 202, which providescommunications between processor unit 204, memory 206, persistentstorage 208, communications unit 210, input/output (I/O) unit 212, anddisplay 214.

Processor unit 204 serves to execute instructions for software that maybe loaded into memory 206. Processor unit 204 may be a set of one ormore processors or may be a multi-processor core, depending on theparticular implementation. Further, processor unit 204 may beimplemented using one or more heterogeneous processor systems in which amain processor is present with secondary processors on a single chip. Asanother illustrative example, processor unit 204 may be a symmetricmulti-processor (SMP) system containing multiple processors of the sametype.

Memory 206 and persistent storage 208 are examples of storage devices. Astorage device is any piece of hardware that is capable of storinginformation either on a temporary basis and/or a permanent basis. Memory206, in these examples, may be, for example, a random access memory orany other suitable volatile or non-volatile storage device. Persistentstorage 208 may take various forms depending on the particularimplementation. For example, persistent storage 208 may contain one ormore components or devices. For example, persistent storage 208 may be ahard drive, a flash memory, a rewritable optical disk, a rewritablemagnetic tape, or some combination of the above. The media used bypersistent storage 208 also may be removable. For example, a removablehard drive may be used for persistent storage 208.

Communications unit 210, in these examples, provides for communicationswith other data processing systems or devices. In these examples,communications unit 210 is a network interface card. Communications unit210 may provide communications through the use of either or bothphysical and wireless communications links.

Input/output unit 212 allows for input and output of data with otherdevices that may be connected to data processing system 200. Forexample, input/output unit 212 may provide a connection for user inputthrough a keyboard and mouse. Further, input/output unit 212 may sendoutput to a printer. Display 214 provides a mechanism to displayinformation to a user.

Instructions for the operating system and applications or programs arelocated on persistent storage 208. These instructions may be loaded intomemory 206 for execution by processor unit 204. The processes of thedifferent embodiments may be performed by processor unit 204 usingcomputer implemented instructions, which may be located in a memory,such as memory 206. These instructions are referred to as program code,computer-usable program code, or computer-readable program code that maybe read and executed by a processor in processor unit 204. The programcode in the different embodiments may be embodied on different physicalor tangible computer-readable media, such as memory 206 or persistentstorage 208.

Program code 216 is located in a functional form on computer-readablemedia 218 that is selectively removable and may be loaded onto ortransferred to data processing system 200 for execution by processorunit 204. Program code 216 and computer-readable media 218 form computerprogram product 220 in these examples. In one example, computer-readablemedia 218 may be in a tangible form, such as, for example, an optical ormagnetic disc that is inserted or placed into a drive or other devicethat is part of persistent storage 208 for transfer onto a storagedevice, such as a hard drive that is part of persistent storage 208. Ina tangible form, computer-readable media 218 also may take the form of apersistent storage, such as a hard drive, a thumb drive, or a flashmemory that is connected to data processing system 200. The tangibleform of computer-readable media 218 is also referred to ascomputer-recordable storage media. In some instances,computer-recordable media 218 may not be removable.

Alternatively, program code 216 may be transferred to data processingsystem 200 from computer-readable media 218 through a communicationslink to communications unit 210 and/or through a connection toinput/output unit 212. The communications link and/or the connection maybe physical or wireless in the illustrative examples. Thecomputer-readable media also may take the form of non-tangible media,such as communications links or wireless transmissions containing theprogram code. The different components illustrated for data processingsystem 200 are not meant to provide architectural limitations to themanner in which different embodiments may be implemented. The differentillustrative embodiments may be implemented in a data processing systemincluding components in addition to or in place of those illustrated fordata processing system 200. Other components shown in FIG. 2 can bevaried from the illustrative examples shown. As one example, a storagedevice in data processing system 200 is any hardware apparatus that maystore data. Memory 206, persistent storage 208, and computer-readablemedia 218 are examples of storage devices in a tangible form.

In another example, a bus system may be used to implement communicationsfabric 202 and may be comprised of one or more buses, such as a systembus or an input/output bus. Of course, the bus system may be implementedusing any suitable type of architecture that provides for a transfer ofdata between different components or devices attached to the bus system.Additionally, a communications unit may include one or more devices usedto transmit and receive data, such as a modem or a network adapter.Further, a memory may be, for example, memory 206 or a cache such asfound in an interface and memory controller hub that may be present incommunications fabric 202.

Computer program code for carrying out operations of the presentinvention may be written in any combination of one or more programminglanguages, including an object-oriented programming language such asJava™, Smalltalk, C++, C#, Objective-C, or the like, and conventionalprocedural programming languages. The program code may execute entirelyon the user's computer, partly on the user's computer, as a stand-alonesoftware package, partly on the user's computer and partly on a remotecomputer, or entirely on the remote computer or server. In the latterscenario, the remote computer may be connected to the user's computerthrough any type of network, including a local area network (LAN) or awide area network (WAN), or the connection may be made to an externalcomputer (for example, through the Internet using an Internet ServiceProvider).

Those of ordinary skill in the art will appreciate that the hardware inFIGS. 1-2 may vary depending on the implementation. Other internalhardware or peripheral devices, such as flash memory, equivalentnon-volatile memory, or optical disk drives and the like, may be used inaddition to or in place of the hardware depicted in FIGS. 1-2. Also, theprocesses of the illustrative embodiments may be applied to amultiprocessor data processing system, other than the SMP systemmentioned previously, without departing from the spirit and scope of thedisclosed subject matter.

As will be seen, the techniques described herein may operate inconjunction within the standard client-server paradigm such asillustrated in FIG. 1 in which client machines communicate with anInternet-accessible Web-based portal executing on a set of one or moremachines. End users operate Internet-connectable devices (e.g., desktopcomputers, notebook computers, Internet-enabled mobile devices, or thelike) that are capable of accessing and interacting with the portal.Typically, each client or server machine is a data processing systemsuch as illustrated in FIG. 2 comprising hardware and software, andthese entities communicate with one another over a network, such as theInternet, an intranet, an extranet, a private network, or any othercommunications medium or link. A data processing system typicallyincludes one or more processors, an operating system, one or moreapplications, and one or more utilities. The applications on the dataprocessing system provide native support for Web services including,without limitation, support for HTTP, SOAP, XML, WSDL, UDDI, and WSFL,among others. Information regarding SOAP, WSDL, UDDI and WSFL isavailable from the World Wide Web Consortium (W3C), which is responsiblefor developing and maintaining these standards; further informationregarding HTTP and XML is available from Internet Engineering Task Force(IETF). Familiarity with these standards is presumed.

Cloud Computing Model

Cloud computing is a model of service delivery for enabling convenient,on-demand network access to a shared pool of configurable computingresources (e.g. networks, network bandwidth, servers, processing,memory, storage, applications, virtual machines, and services) that canbe rapidly provisioned and released with minimal management effort orinteraction with a provider of the service. This cloud model may includeat least five characteristics, at least three service models, and atleast four deployment models, all as more particularly described anddefined in “Draft NIST Working Definition of Cloud Computing” by PeterMell and Tim Grance, dated Oct. 7, 2009.

In particular, the following are typical Characteristics:

On-demand self-service: a cloud consumer can unilaterally provisioncomputing capabilities, such as server time and network storage, asneeded automatically without requiring human interaction with theservice's provider.

Broad network access: capabilities are available over a network andaccessed through standard mechanisms that promote use by heterogeneousthin or thick client platforms (e.g., mobile phones, laptops, and PDAs).

Resource pooling: the provider's computing resources are pooled to servemultiple consumers using a multi-tenant model, with different physicaland virtual resources dynamically assigned and reassigned according todemand. There is a sense of location independence in that the consumergenerally has no control or knowledge over the exact location of theprovided resources but may be able to specify location at a higher levelof abstraction (e.g., country, state, or datacenter).

Rapid elasticity: capabilities can be rapidly and elasticallyprovisioned, in some cases automatically, to quickly scale out andrapidly released to quickly scale in. To the consumer, the capabilitiesavailable for provisioning often appear to be unlimited and can bepurchased in any quantity at any time.

Measured service: cloud systems automatically control and optimizeresource use by leveraging a metering capability at some level ofabstraction appropriate to the type of service (e.g., storage,processing, bandwidth, and active user accounts). Resource usage can bemonitored, controlled, and reported providing transparency for both theprovider and consumer of the utilized service.

The Service Models typically are as follows:

Software as a Service (SaaS): the capability provided to the consumer isto use the provider's applications running on a cloud infrastructure.The applications are accessible from various client devices through athin client interface such as a web browser (e.g., web-based e-mail).The consumer does not manage or control the underlying cloudinfrastructure including network, servers, operating systems, storage,or even individual application capabilities, with the possible exceptionof limited user-specific application configuration settings.

Platform as a Service (PaaS): the capability provided to the consumer isto deploy onto the cloud infrastructure consumer-created or acquiredapplications created using programming languages and tools supported bythe provider. The consumer does not manage or control the underlyingcloud infrastructure including networks, servers, operating systems, orstorage, but has control over the deployed applications and possiblyapplication hosting environment configurations.

Infrastructure as a Service (IaaS): the capability provided to theconsumer is to provision processing, storage, networks, and otherfundamental computing resources where the consumer is able to deploy andrun arbitrary software, which can include operating systems andapplications. The consumer does not manage or control the underlyingcloud infrastructure but has control over operating systems, storage,deployed applications, and possibly limited control of select networkingcomponents (e.g., host firewalls).

The Deployment Models typically are as follows:

Private cloud: the cloud infrastructure is operated solely for anorganization. It may be managed by the organization or a third party andmay exist on-premises or off-premises.

Community cloud: the cloud infrastructure is shared by severalorganizations and supports a specific community that has shared concerns(e.g., mission, security requirements, policy, and complianceconsiderations). It may be managed by the organizations or a third partyand may exist on-premises or off-premises.

Public cloud: the cloud infrastructure is made available to the generalpublic or a large industry group and is owned by an organization sellingcloud services.

Hybrid cloud: the cloud infrastructure is a composition of two or moreclouds (private, community, or public) that remain unique entities butare bound together by standardized or proprietary technology thatenables data and application portability (e.g., cloud bursting forload-balancing between clouds).

A cloud computing environment is service-oriented with a focus onstatelessness, low coupling, modularity, and semantic interoperability.At the heart of cloud computing is an infrastructure comprising anetwork of interconnected nodes. A representative cloud computing nodeis as illustrated in FIG. 2 above. In particular, in a cloud computingnode there is a computer system/server, which is operational withnumerous other general purpose or special purpose computing systemenvironments or configurations. Examples of well-known computingsystems, environments, and/or configurations that may be suitable foruse with computer system/server include, but are not limited to,personal computer systems, server computer systems, thin clients, thickclients, hand-held or laptop devices, multiprocessor systems,microprocessor-based systems, set top boxes, programmable consumerelectronics, network PCs, minicomputer systems, mainframe computersystems, and distributed cloud computing environments that include anyof the above systems or devices, and the like. Computer system/servermay be described in the general context of computer system-executableinstructions, such as program modules, being executed by a computersystem. Generally, program modules may include routines, programs,objects, components, logic, data structures, and so on that performparticular tasks or implement particular abstract data types. Computersystem/server may be practiced in distributed cloud computingenvironments where tasks are performed by remote processing devices thatare linked through a communications network. In a distributed cloudcomputing environment, program modules may be located in both local andremote computer system storage media including memory storage devices.

Referring now to FIG. 3, by way of additional background, a set offunctional abstraction layers provided by a cloud computing environmentis shown. It should be understood in advance that the components,layers, and functions shown in FIG. 3 are intended to be illustrativeonly and embodiments of the invention are not limited thereto. Asdepicted, the following layers and corresponding functions are provided:

Hardware and software layer 300 includes hardware and softwarecomponents. Examples of hardware components include mainframes, in oneexample IBM® zSeries® systems; RISC (Reduced Instruction Set Computer)architecture based servers, in one example IBM pSeries® systems; IBMxSeries® systems; IBM BladeCenter® systems; storage devices; networksand networking components. Examples of software components includenetwork application server software, in one example IBM WebSphere®application server software; and database software, in one example IBMDB2® database software. (IBM, zSeries, pSeries, xSeries, BladeCenter,WebSphere, and DB2 are trademarks of International Business MachinesCorporation registered in many jurisdictions worldwide)

Virtualization layer 302 provides an abstraction layer from which thefollowing examples of virtual entities may be provided: virtual servers;virtual storage; virtual networks, including virtual private networks;virtual applications and operating systems; and virtual clients.

In one example, management layer 304 may provide the functions describedbelow. Resource provisioning provides dynamic procurement of computingresources and other resources that are utilized to perform tasks withinthe cloud computing environment. Metering and Pricing provide costtracking as resources are utilized within the cloud computingenvironment, and billing or invoicing for consumption of theseresources. In one example, these resources may comprise applicationsoftware licenses. Security provides identity verification for cloudconsumers and tasks, as well as protection for data and other resources.User portal provides access to the cloud computing environment forconsumers and system administrators. Service level management providescloud computing resource allocation and management such that requiredservice levels are met. Service Level Agreement (SLA) planning andfulfillment provides pre-arrangement for, and procurement of, cloudcomputing resources for which a future requirement is anticipated inaccordance with an SLA.

Workloads layer 306 provides examples of functionality for which thecloud computing environment may be utilized. Examples of workloads andfunctions which may be provided from this layer include: mapping andnavigation; software development and lifecycle management; virtualclassroom education delivery; data analytics processing; transactionprocessing; and others (e.g., enterprise-specific functions in a privatecloud).

It is understood in advance that although this disclosure includes adetailed description on cloud computing, implementation of the teachingsrecited herein are not limited to a cloud computing environment. Rather,embodiments of the present invention are capable of being implemented inconjunction with any other type of computing environment now known orlater developed.

Thus, a representative cloud computing environment has a set of highlevel functional components that include a front end identity manager, abusiness support services (BSS) function component, an operationalsupport services (OSS) function component, and the compute cloudcomponent. The identity manager is responsible for interfacing withrequesting clients to provide identity management, and this componentmay be implemented with one or more known systems, such as the TivoliFederated Identity Manager (TFIM) that is available from IBMCorporation, of Armonk, N.Y. In appropriate circumstances TFIM may beused to provide federated single sign-on (F-SSO) to other cloudcomponents. The business support services component provides certainadministrative functions, such as billing support. The operationalsupport services component is used to provide provisioning andmanagement of the other cloud components, such as virtual machine (VM)instances. The cloud component represents the main computationalresources, which are typically a plurality of virtual machine instancesthat are used to execute a target application that is being madeavailable for access via the cloud. One or more databases are used tostore directory, log, and other working data. All of these components(included the front end identity manager) are located “within” thecloud, but this is not a requirement. In an alternative embodiment, theidentity manager may be operated externally to the cloud. The serviceprovider also may be operated externally to the cloud.

Some clouds are based upon non-traditional IP networks. Thus, forexample, a cloud may be based upon two-tier CLOS-based networks withspecial single layer IP routing using hashes of MAC addresses. Thetechniques described herein may be used in such non-traditional clouds.

In a non-limiting implementation, representative platform technologiesare, without limitation, IBM System X® servers with VMware vSphere 4.1Update 1 and 5.0.

Representative cloud applications include IBM Sametime® Meetings, IBMSmartCloud for Social Business, or the like.

Cloud Deployment Technologies

It is known to provide an appliance-based solution to facilitate rapidadoption and deployment of both Infrastructure and Platform as Serviceofferings. As described above, one such appliance is IBM WorkloadDeployer (IWD), and this appliance also may be used to manage a shared,multi-tenant environment, where isolation and security are of utmostimportance. The secure nature of the physical appliance (sometimesreferred to herein as a box) typically is provided by a self-disablingswitch, which is triggered if the appliance cover is removed. Thisphysical security enables the appliance to serve as a secure vault forcredentials, which can be tied to virtual images throughout their entirelifecycle (in storage, being dispensed, running in the cloud, or beingremoved from the cloud). IBM Workload Deployer also contains a storagedriver that streamlines the storage of image customizations. It alsoserves as a dedicated store for both pre-loaded and customizedmiddleware virtual images and patterns. The appliance also includesadvanced compression and storage techniques that enable a large numberof these virtual images (each of which may be sizeable) to be stored.

In operation, the appliance can provision standard and customizedmiddleware virtual images and patterns that can be securely deployed andmanaged within private or on-premise cloud computing environments. Thesevirtual images can help organizations to develop, test, and deploybusiness applications easily and quickly, thus ending the manual,repetitive, and error prone processes that are often associated withcreating these complex environments. Upon completion, resources arereturned to the shared resource pool automatically for future use andare logged for internal charge-back purposes. The appliance also managesindividual user and group access to resources, providing IT managerswith the control needed to optimize efficiency at a fine-grain level.

Typically, the appliance includes hardware and firmware cryptographicsupport to encrypt all the data on hard disk. This data includes,without limitation, event log data. No users, including administrativeusers, can access any data on physical disk. In particular, theoperating system (e.g., Linux) locks down the root account and does notprovide a command shell, and the user does not have file system access.When an administrator performs a backup of the appliance, the backupimage is encrypted to protect the confidentiality of the data. Whenrestoring an encrypted image, a decryption key thus is needed to decryptthe backup image to enable the data to be restored to the appliance.

Referring to FIG. 4, a representative operating environment includes thephysical appliance 400, which interfaces to the cloud 402. The appliancemay be implemented using a data processing system such as describedabove with respect to FIG. 2. Preferably, the appliance 400 includes aWeb 2.0-based user interface (UI), a command line interface (CLI), andREST-based application programming interfaces (APIs). The applianceprovides a management function that enables the rapid deployment ofcloud-based solutions. To that end, the appliance provides storage for(i) data 404 used to manage user and group access to resources, (ii) forpre-loaded and/or customizable middleware virtual images 406, and (iii)for configurable patterns and script packages 408. Patterns are logicaldescriptions of both the physical and virtual assets that comprise aparticular solution. As will be described in more detail below,preferably patterns are structured according to the TOSCA specification.The management function and interfaces provide a template-based approachto construction that permits the rapid creation and modification of anotherwise complex set of hardware and software components. Inparticular, the use of patterns allows an organization to construct anindividual element or integrated solution one time, and then to dispensethe final product on demand. Typically, there are two types of patterns:virtual system patterns provide the most flexibility and customizationoptions of the two types. It consists of an operating system and,potentially, additional software solutions, such as WebSphere®Application Server. Virtual application patterns are optimized and areconstructed typically for the purpose of supporting a singular workload.

As also seen in FIG. 4, the on-premise or private cloud environment 402on which the middleware application runs typically constituteshypervisors, networking infrastructure, and storage devices that areallocated to the appliance. A representative environment may beimplemented in the manner described above with respect to FIG. 3.

FIG. 5 illustrates how the appliance can be used to build a customprivate cloud. At step 1, the hardware, hypervisors and networking forthe cloud are identified. At step 2, the user selects and customizes thevirtual images. At step 3, the user adds one or more script packages asneeded to customize the deployed middleware environment. At step 4,pre-installed or customized patterns are used to describe the middlewaretopology to be deployed. Patterns can be built from virtual images, e.g.using a drag-and-drop interface. At step 5, the virtual systems aredeployed to the cloud.

The references herein to IBM Workload Deployer are exemplary and shouldnot be taken to limit the disclosed technique, which may be implementedon any appliance (or, more generally, machine) having the generalcharacteristics and operating functionality that has been described.Specific references to IWD should be construed to include both theabove-identified product, as well as other technologies that implementthe functionality referenced above.

As additional background, the Oasis Topology and OrchestrationSpecification for Cloud Applications (TOSCA) is a specification designedto enhance the portability of cloud applications and services. Itenables the interoperable description of application and infrastructurecloud services, the relationships between parts of the service, and theoperational behavior of these services (e.g., deploy, patch, shutdown),independent of the supplier creating the service and any particularcloud provider or hosting technology. Among other benefits, TOSCAenables portable deployment to any compliant cloud, and facilitatessmooth migration of existing applications to the cloud. Using TOSCA,cloud applications can be modeled, shared, deployed and managed,seamlessly, amongst products and cloud platforms, from multiple vendors.

A TOSCA document is a descriptor that describes all applicationcomponents to be deployed to the cloud and their interrelationships. Inthe descriptor, each application component typically is uniquelyidentified by an identifier composed of a name, version, architecture,as well as a vendor of the component. This identifier is useful as asearch key with respect to a database of information; as will bedescribed below, one such database is a database of known defects and/orvulnerabilities for that specific application component.

It is known to provide a cloud management platform that implementsTOSCA-compliant solutions. As one example, the cloud management platformis the IBM®SmartCloud® Orchestrator open cloud management platform,which leverages additional standards technologies such as OpenStack, andOSLC (Open Service for Lifecycle Collaboration). A management platformof this type typically comprises three main functional layers: aninfrastructure services layer, which is preferably based on OpenStack,for provisioning, configuring and managing storage, compute and networkresources, a platform services layer, which includes virtual machineimage lifecycle management capabilities and pattern services, and anorchestration services layer. As described above, a “pattern” providesdeployment and management instructions for the business service. Apattern preferably is an XML-based definition of an infrastructureconfiguration required to provision and managed the various resources(e.g., compute, networking, storage, OS, middleware, and the like) for aspecific application (or application-type) workload. The orchestrationservices layer provides a business process management solution.

Of course, the above-described cloud management environment is notintended to be limiting, as the techniques herein may be implemented inother (open, closed, or hybrid) environments, and/or using otherdeployment technologies (whether open or proprietary, or mixed).

Context-Based Cloud Security Assurance Service

With the above as background, the subject matter of this disclosure isnow described. This subject matter is sometimes referred to herein as a“context-based cloud security assurance service” or a “securityassurance service or system” or just the “service” or “system” as ashort-hand. Without limitation, the subject matter may be implementedwithin or in association with a cloud deployment platform system orappliance (FIG. 4) as has been described, or using any other type ofdeployment systems, products, devices, programs or processes. Arepresentative cloud application platform with which the securityassurance service may be implemented includes, without limitation, IBM®SmartCloud Orchestrator, which as noted above is a platform systemspecifically design and tuned for running applications, and thatsupports the use of patterns for easy deployment into its cloudenvironment. The reference to this commercial system is not intended tobe limited, as the security assurance service of this disclosure mayinteroperate with any cloud infrastructure.

The techniques herein may be implemented as a management solution,service, product, appliance, device, process, program, execution thread,or the like. Typically, the techniques are implemented in software, asone or more computer programs executed in hardware processing elements,in association with data stored in one or more data sources, such as aproblems database. Some or all of the processing steps described may beautomated and operate autonomously in association with other systems.The automation may be full- or partial, and the operations (in whole orin part) may be synchronous or asynchronous, demand-based, or otherwise.

The following is a high-level description of the cloud securityassurance service. Generally, the service operates generally to gather(or otherwise obtain from other data sources) information aboutavailable cloud platforms, topologies and capabilities. The service alsoidentifies security capabilities that are available to be setup. Thesesecurity capabilities include, without limitation, virtual perimeternetworks (DMZs), network segregation, storage isolation, IntrusionPrevention System (IPS) deployment, Security Information and EventManagement (SIEM) deployment, reverse proxies, firewalls, SSLcommunication, configuration with existing SIEM, multi-factorauthentication, risk-based authentication, and others. Preferably, theservice simplifies (or abstracts) the available capabilities intoeasy-to-understand security assurance categories for the environment'sexisting topology.

The assurance service exposes the categories to the user (duringapplication deployment) as “templates.” Preferably, the service isdeployed with a set of default templates. Preferably, a template definesthe requirements for a particular security assurance level, e.g., a“medium security” template might include the following specifiedrequirements: “SSL, SIEM, IPS, disk encryption, multi-factorauthentication, no resource segregation and isolation.” A securityadministrator (for the service) might later alter the set of defaulttemplates (by adding in different templates), or possibly to change theconfiguration of an existing templates to add or remove requirements.Preferably, however, the security assurance service does not need tointerpret the specific requirements of a template; rather, and as willbe described in more detail below, the security assurance serviceinterprets the “context” of a particular deployment to make adetermination regarding what security resources (and/or their particularsettings) satisfy the requirements of the template. In this approach,the templates are loaded into the assurance service (e.g., by securityexperts) and are meant to be highly instructive to the system. In use,preferably the templates get exposed to the end user with simplifiednames (or identifiers, descriptors, or the like), such as “highsecurity,” “medium security” or “low security.” Preferably, these termsare presented (verbatim, more or less) to the end user. It is notrequired that the end user have an understanding of the resources (ortheir operational characteristics) underlying the security assurancelevel represented by the template. The system, however, understandsthese details and operates to apply specific capabilities and controlsto translate the user-selected specification (e.g., “high security”)into granular requirements. This intentionally simple end userterminology might be exposed to the end user in the form of a button orother control, and, as noted, the terminology presented to the end useris not intended to describe the particular underlying requirements orresources that are expected to provide the security assurance level.Rather, the end user only needs to know what generalized assurance levelhe or she desires to implement for the application under deployment.

Based on the requirements specified, a template has a given set of oneor more security configuration changes associated therewith. As will bedescribed, the end user (typically the application developer) selectsone or more of such security templates that he or she would like theservice to configure/provision the application against. The service mayprovide a recommendation to the user in this regard. Based on the userselections, the service then interprets the requested one or moresecurity assurance templates and, in response, the service generates aconcrete list of one or more security configuration changes (typicallychanges/updates to security settings to existing securityinfrastructure). Optionally, the service also generates a note to thesecurity administrator(s) of the capabilities being used for theapplication. During the application deployment, the service applies thesecurity changes, preferably using REST-based (or equivalent) interfacesto existing (configured) security products; in addition and, asnecessary to meet the security assurance level specified by thetemplate(s), the service may also deploy new security software instances(as applicable and if licenses are available). Further, and once againas necessary to meet the security assurance level selected, the servicemay also provision hardware and network environments, preferably usingexisting cloud facilities, and as needed by the application. In thismanner, the security assurance service creates a context-specific securecloud application zone for the application-being-deployed. Preferably,the application deployment platform is called-back when the securityconfiguration update completes; the platform then completes thedeployments. The newly-deployed and secured application is thenactivated (possibly by the service directly).

As described, the assurance service as described herein preferablyoperates in a context-based manner, taking into consideration the“context” in which the application is to be deployed. Representative“context” information includes, without limitation, the nature of thetarget platform, the nature of the environment in which the workload isanticipated to execute, the nature of any compliance or other regulatoryrequirements for the workload, any company security requirements(configured by administrators), context of the deployed application(software, configuration, topology, etc.) that will or may affect howsecurity resources interact with the application, and so forth. Thus,for example, if the workload is being deployed on the Amazon® cloud(which is public), the service might consider public cloud requirements,such as SSL communication for all traffic, even though such requirementswould not necessarily be enforced in a private cloud. As anotherexample, if the workload is running in a test or developmentenvironment, the service may only provision minimal controls arounddata, as the application (in this context) would not be handling real(live) customer data. As yet another example, if the workload needs tobe PCI-compliant, then the service may provision that workload only on acertain network but not allow (or otherwise block) the move of theworkload to a network or VLAN that is not secure. Of course, the aboveare merely representative examples. Preferably, the security contextinformation is gathered by the security assurance service directly, orsuch information is made available to the security assurance servicefrom other connected data sources that have that information (or accessto that information).

FIG. 6 illustrates the basic components of a cloud security cloudassurance service 600 of this disclosure according to one embodiment.Reference numeral 601 illustrates the cloud platform and the systemsrunning on the cloud platform (i.e., the customer workload). The cloudplatform and its associated customer workloads are protected by theassurance service, which provides for a centralized or federated servicethat manages all (or defined ones of) security resources impacted byapplication deployment(s) into that platform. These resources may bequite varied and include, among others, reverse proxies, HTTP servers,authorization updates, addition of new identities, provisioning of VPNs,log integration with a SIEM solution, DMZs, firewall configuration toopen ports, and so forth. As will be described, preferably the serviceinvokes remote interfaces (e.g., REST-based interfaces) to updateconfigurations for the security resources. The determination of whichsecurity resources get updated and how depends on the template-basedapproach as described. The various workloads 603 executing on the cloudplatform are set up by the cloud platform customer(s), typically inadvance. The cloud platform is represented by the icons such as IBMPure™, Amazon® web services, VMWare®, which are merely representative.

The cloud security assurance service 600 includes a context monitorcomponent (or “context monitor”) 605 that is operative to query thecloud platform for available capabilities, and catalogs them in anassurance service database 607. In operation, the context monitor 605queries the cloud platform 601 using cloud-provided applicationprogramming interfaces (APIs) to determine the resources available, ascloud platforms generally expose this information in this manner. Thecontext monitor then maps available software to security capabilities.The product-to-capability mapping may be provided by the cloud platformdirectly, or that knowledge may be embedded in the assurance servicedatabase 607. Thus, for example, the cloud platform may include IBMQRadar, which provides SIEM capability. The assurance service includesconfiguration information that specifies which security assurance levelsrequire which particular capability. Thus, for example, a “high” or“medium” assurance level may require a SIEM solution while a “low” leveldoes not. As noted above, the requirement(s) for a particular securityassurance level are linked to a predefined template, preferably inadvance (by a security expert). As described, and in this particularexample scenario, when the end user picks a particular security solution(e.g., “high”), the security assurance service leverages the cloudplatform to install the product (or to adjust its security settings ifalready installed) to satisfy the SIEM requirement for that securitylevel.

To that end, the service 600 provides the security assurance templates602. As noted above, preferably a default set of templates 602 areprovided by the service, and each template defines the requirements fora particular security assurance level. Typically, templates will be ofvarying types or categories. As explained, a template is highlyinstructive (to the system) in that it includes a defined set ofrequirements for the security assurance level. Thus, a “medium” securitylevel may be specified in a template that defines requirements such as“SSL, SIEM, IPS, disk encryption” and so forth. Preferably, and asdescribed above, the service does not need to interpret theserequirements; rather, the service interprets the context of thedeployment (as specified or ascertained by the context monitorcomponent) to make a determination regarding what security resources (ortheir settings) satisfies these requirements. Preferably, thetemplate(s) come pre-configured. The set of templates 602 may beaugmented with additional templates, or a particular template'srequirements may be adjusted as needed.

Preferably, and as used herein, the security assurance templates 602 aremodules within the service that provide easy-to-understand securitycategories or profiles, and their associated security levels, such as“high/medium/low internal network security” and “high/medium/lowfirewall security,” and the like. The service 600 also includes anassurance configuration broker 604, which identifies the security goalsof selected templates, and that operates to translate selection of atemplate into detailed configuration steps, preferably based on systemconfiguration and context of available resources. This translationoperation is described in more detail below. Further, the servicepreferably includes (or has associated therewith) a security managementinterface 608 (e.g., cloud tooling UI, such as IBM SmartCloudOchestrator), which is a configuration point that is used to add orremove security templates, to provide manual configuration of managedsecurity resources, and/or to override (under permitted circumstances) asecurity template selected by an end user. The security assuranceservice also includes a cloud security process workflow 610, which is amodule that invokes appropriate (e.g. REST-based) interfaces to applychanges to underlying security infrastructure (security resources) asindicated by the configuration broker 604. An assurance pattern module612, which provides an administrative interface, is a cloud-specificservice that coordinates application deployment and provisioning withthe security assurance service 600. Typically, the assurance patternmodule 612 comprises an administrative interface component of the cloudapplication platform, although this is not a requirement. The assurancepattern module 612 queries the assurance service for available assurancetemplates 602 based on the application being deployed.

In FIG. 6, the application owners/administrators at the top leftrepresents the application deployer(s); these are individuals who onlyneed to have access to the easy-to-understand security assurance leveltemplates (by category/security level). The cloud teams or otheradministrators at the bottom left represent individuals either whocreate the templates, or who are provided the capability to add newtemplates and/or modify the particular requirements in a pre-configuredtemplate. The cloud teams or other administrators interact with thesystem or service through an administrative interface. Each of theabove-described components typically is implemented as software, i.e.,as a set of computer program instructions executed in one or morehardware processors. The components are shown as distinct, but this isnot a requirement, as the components may also be integrated with oneanother in whole or in part. One or more of the components may executein a dedicated location, or remote from one another. One or more of thecomponents may have sub-components that execute together to provide thefunctionality. There is no requirement that particular functions of thesecurity assurance service be executed by a particular component asnamed above, as the functionality herein (or any aspect thereof) may beimplemented in other or systems.

The security assurance service may be implemented by a cloud serviceprovider that operates infrastructure for a private cloud, a publiccloud, or a hybrid cloud. This security assurance system deploys andmanages security infrastructure. Preferably, and as described above, theassurance system interacts with the cloud's security administrator (orthe like) through an administrative interface, and with the applicationowner through cloud tooling UI. Preferably, the application ownerinteracts primarily with the cloud tooling UI (see FIG. 7, which ismerely representative) to define the high-level security requirementsand to deploy the application. FIG. 7 is representative of an editorthat is web-based, although the particular implementation of the editor(or an equivalent application that facilitates presentation andmanagement of the templates in the manner described) may be of any type.

Using the cloud tooling UI (or its equivalent), the user also may querythe cloud application environment (e.g., to request details about theapplication being deployed) and, in response, receive information aboutone or more available security capabilities available in the cloudapplication environment (e.g., particular security resources appropriatefor the application being deployed). These available capabilities mayinclude, e.g., available hardware, available software, existinglicenses, and available licenses.

Thus, and as has been described, different types of users may interactwith the service in different ways. In one embodiment, a first type ofuser (e.g., the application owner) works with the service by viewing andinteracting with the template, while a second type of user (e.g., thesecurity administrator) works with the service by viewing andinteracting using one or more security administrative views, e.g., ofsecurity changes associated with the selection of templates by the firsttype of users. A security administrative view enables the system toreceive inputs from the security administrator that may triggerenforcement of one or more security administration actions with respectto configuration of one or more security capabilities in the cloudapplication environment. Such inputs may include, for example, an inputto approve a pending security configuration change, an input thatoverrides a selection by a first user of a template, or that overrides aselection of a security capability associated with a template, or thatinhibits deployment of an application into the cloud applicationenvironment when a template having a minimum security assurance levelassociated therewith has not been selected by a first user, or the like.The security administrative view may also provide one or more additionaladministration functions such as: configuring a new template ormodifying an existing template, using security analytics to manageapplication deployment based on enterprise security policy, definingsecurity requirements for the cloud application environment, auditingsecurity capabilities available in the cloud application environment,and the like. In one embodiment, an input received in the securityadministrative view initiates a security scan of the cloud applicationenvironment, and the results of that security scan (e.g., any securitycapability gap analysis) may then be presented to the administrator. Asanother use case, an input may also be used to retroactively apply anupgraded template to an existing application that has been deployed inthe cloud application environment.

In one particular (but non-limiting) implementation scenario, anenterprise has an associated private cloud (implemented within a cloudservice) that is managed by a cloud application platform. That platformmay then be augmented to interoperate with (or to actually include) thesecurity assurance service of this disclosure.

More generally, the security assurance service may be implemented by anenterprise in a standalone manner. It may be available as a managedservice provided by a cloud service or some other service provider.

As described, preferably the service operates by having an end userprovide a generalized specification of a security level (e.g., “highnetwork security”) that the service then uses (after interpretingapplication requirements and available resources) to generate asecurity-optimized deployment for an application. Typically, and asnoted above, the application is being deployed into an existingenvironment, and the security assurance service operates to defineand/or tailor the security configuration changes required for thatexisting environment (into which the application will be deployed). Thesecurity-optimized deployment for the application is sometimes referredto herein as a secure context-based “cloud application zone.”

As described, “security levels” as used herein are sometimes referred toas “security assurance levels.” These levels, as noted above, areexposed as easy-to-understand or “coarse” grained descriptors (“high” or“low”), as compared to more fine-grained specificity that mightotherwise be known or available to, say, a security expert. The terms“coarse” or “fine” are relative phrases, but the notion of a “coarse”designation of a security assurance level is one that merely providesthe basic information available to the user who might not otherwise knowor be able to ascertain (or care about) the explicit securityrequirements underlying a particular “coarse” security assurance level.It is sufficient for the user (the application owner) in thiscircumstance to know only that the security assurance level he or shedesires (for a particular category) be “high” or “low” or some othersuch classification (however delineated). Thus, the term “high” (inreference to a particular coarse security assurance level) may bedesignated in the alternative by a numerical value, some otheridentifier or designation. As explained, these terms, however, are meantto be presented, more or less verbatim, to the end user. The system thenapplies specific capabilities and controls to translate theuser-selected security solution into the granular requirements for theunderlying security resources. A preferred way to specify the solutionis by a button or other common display artifact.

In a representative embodiment, the service exposes, provides orinteroperates with a set of security templates, which may be categorizedaccording to type. These templates are provided by the assurancetemplate module shown in FIG. 6. Thus, for example, the service mayexpose security templates having the following categories: “InternalNetwork Security,” “Application Security,” “Data Security” and “IntruderProtection.” These are merely representative. A particular templatecategory may then be identified according to a defined security level:such as “Low” or “High.” The service may provide just “Low” or “High”templates, or it may provide further levels (e.g., Low, Medium and High,or further more specific levels, etc.). A particular enterpriseapplication being deployed thus may have one or more such securitytemplates associated therewith, each defining a category and a specifiedsecurity level. Thus, for example, a particular application beingdeployed may have the following specification: Internal Network Security(Low), Application Security (High), Data Security (High) and IntruderProtection (High). A web-based or other configuration interface may beused to specify the one or more security templates that are to beassociated with a particular application being deployed. This interfacemay be associated with a conventional workload deployment tool, such asIBM® Workload Deployer Virtual Application Builder. FIG. 7 illustrates arepresentative user interface for this purpose, which may comprise aportion of the security management interface (see, FIG. 6). As notedabove, this interface provides the configuration point for adding orremoving security templates, providing manual configuration of managedsecurity resources, or (if configured) overriding security templatesselected by end users. In an alternative embodiment, the categories andsecurity levels are defined automatically or programmatically, or suchinformation is made available from a repository of such data publishedby another source.

As has been described, the template defines a set of requirements thatprovide a specific “security assurance” level, with that assurance levelthen being realized or implemented with respect to one or more securityresources. A security resource may be a system, device, appliance,program, process or other computing entity within the securityinfrastructure. Preferably, the security assurance service interpretsthe context of the deployment to make a determination regarding whatsecurity resources (and what settings therein) are needed to satisfy therequirements of a particular template. Thus, and based at least in parton the particular deployment context, a security template has associatedtherewith one or more security configurations (security resourcesettings) that implement the category (and at the specified level) forthat context. Preferably, and as described above, these securityconfigurations are identified by the security assurance configurationbroker component (see, FIG. 6), which takes (as input) the generalizedsecurity goals of the selected template and translates that selectioninto detailed configuration steps (or changes) based on the systemconfiguration and the context of available security resources (assupplied by the context monitor).

Thus, for example, if the application category is “Internal NetworkSecurity” and the security level is, say, “Low,” the broker determinesthat the detailed security steps necessary to implement that templatemight include: (i) creating a “junction” between a front-end proxyserver and a back-end Web application server based on applicationendpoint, (ii) use basic authentication for the junction and configure atrust association interceptor (TAI) in the application server for singlesign-on (SSO), and (iii) enable restrictive firewalls, and open ports tothe application endpoint. As another example, if the applicationcategory is “Application Security” and the security level is, say,“High,” the detailed security steps necessary to implement that templatemight include: (i) run a security analytic tool (e.g., AppScan) againstendpoints and halt deployment if any critical vulnerabilities areidentified, (ii) instruct the cloud application platform to provision aVPN to host the application in the cloud, (iii) configure access managerpolicies for authorized roles defined by the application, and (iv)create an additional software-based DMZ in the cloud dedicated to theapplication. As yet another example, if the application category is“Data Security” and the security level is, say, “Low,” the detailedsecurity steps necessary to implement that template might include (i)update application server to use an SSL connection to the database, orthe like. As still another example, if the application category is“Intruder Protection” and the security level is, say, “High,” thedetailed security steps necessary to implement that template mightinclude: (i) configure the security intelligence platform (e.g., IBM®QRadar) log sources, (ii) update SIEM filters for the application, and(iii) update IPS rules for the application. Of course, these are merelyrepresentative (non-limiting) examples of the security configurationchanges. The particular changes that are implemented by the securityassurance service will depend on the implementation and availableresources (products, systems, configurations, and the like).

Thus, according to this disclosure, when the cloud provider deploys theapplication (or initiates the deployment), it notifies the securityassurance service of the one or more selected (or otherwise defined orprescribed) security templates. Preferably, the cloud provider alsosends the assurance service details of the application. The securityassurance service takes the selected templates as guidance, and thebroker component then tailors the detailed security configurationchanges required for the existing environment to support the applicationwithin the selected security constraints that have been specified andthe context of available resources (as determined by the contextmonitor). If desired, these security configuration changes may bepresented to a security administrator for verification before beingimplemented. Upon verification (if that optional operation isimplemented), the security assurance service preferably invokes remoteinterfaces for software configuration. In addition, and if necessary,the service communicates with the cloud provider to obtain informationabout any prerequisites (of the cloud provider) that may need to beaddressed when deploying the application. These prerequisites mayinclude, for example, creation of a VPN, or other security requirementsunique to the provider.

A template may also include other information, such as cost informationassociated with a particular security capability. The cost informationin a template may be derived as an estimate of one or more costsassociated with a set of one or more security configuration changes inthe cloud application environment. That cost information also may beadjusted from time-to-time, e.g., based on changing costs of securitycapabilities in the cloud application environment, or as a result ofother changed conditions. When the system exposes such cost information,preferably cost information resulting from the selection of thetemplates (e.g., by one or more users) may be collected and presented topermitted individuals in appropriate display views in the editor (orsome other application).

The system (e.g., the UI editor) may also provide for the capability toreceive information setting a security cost of one or more securitychanges. Based on this information, the set of templates that areexposed to the user may be adjusted.

The following provides a description of a representative use case,merely for explanatory purposes. The details of this example scenarioare not intended to be limiting, and all products and services arespecified for discussion purposes only. As illustrated in FIG. 8, anenterprise (Acme Bank) has a Production Zone 800 implemented in aprivate cloud environment. The private cloud is accessible from theInternet via a DMZ 802 located between a pair of firewalls 804 and 806.According to this disclosure, a Security Zone 808 hosts the securityassurance service 810. As shown, it is assumed that the enterprise alsohas a comprehensive suite of security software already deployed. Thissuite includes, for example, IBM Security Access Manager (ISAM) foraccess management 812, IBM Security Identity Manager (ISIM) for identitymanagement 814, IBM Security Web Gateway appliance (the DMZ for secureproxy) 816, IBM DB2 database for user storage 818, IBM QRadar SIEM 820hosted on IBM PureApplication, a standardized cloud application platform822, IBM Security AppScan 824, and a network IPS 826 in the DMZ 802.Jane 828 is an application developer/administrator at Acme and is taskedwith deploying the PocketBook™ application 830. To that end, and usingthe cloud application platform tools, Jane builds a virtual system thatincludes appropriate enterprise nodes (e.g., Red Hat Enterprise nodes(RHELs) for various components or application instances, such as (inthis example scenario) a node 832 for a WebSphere Application Server(WAS) instance, a node 834 for IBM HTTP Server (IHS) instance, and anode 836 for IBM DB2 instance, etc. The virtual system preferablyencompasses the pieces needs for application functionality andscalability (for the new application) in the Acme private cloud. In thisexample scenario, however, it is assumed that the cloud pattern createdby Jane does not cover or otherwise surface the security pieces that areneeded to protect what will be an externally-facing web application.Thus, the security assurance service of this disclosure will be needed.

As also seen in FIG. 8, John 838 is a security architect at Acme and istasked with security for production systems at the company. To assistwith system-wide configuration, John deploys the security assuranceservice 810 of this disclosure (see, e.g., FIG. 6) and, in particular,he configures the service to manage all software-based security-relatedresources in the cloud, together with integration with existingdeployments such as (in this example scenario) ISAM, ISIM, Web SecurityGateway, QRadar, AppScan and IPS. When Jane 828 uses the cloud patterneditor (provided by the PureApplication system 822) to prepare thePocketBook application 830 for deployment, it is assumed that she is notfamiliar with the internal workings of the security deployments toproperly configure those pieces of the security puzzle. Jane, however,does know (or require) that this application needs to be highly-securedfor any communication with the Internet, but perhaps not as secure withrespect to requests from the internal network. Using the techniques ofthis disclosure, Jane selects one or more security templates that areneeded (or desired) to create the secure cloud application zone for thisnewly-deployed application. As noted above, preferably the securityassurance service integrates with the other cloud deployment toolingsuch that, during deployment, Jane can select from one or moreeasy-to-understand security assurance templates alongside otherdeployment modules (see, e.g., FIG. 7). In this example, Jane is assumedto have selected the four (4) security modules shown in FIG. 7 anddescribed above. As explained above, the security assurance servicetakes the selected templates as guidance in tailoring the detailedsecurity configuration changes required for the existing environment(FIG. 8). The application is then deployed within the configured cloudapplication zone with its context-based security assurance.

FIG. 8 illustrates the detailed operational steps. At step (1), andusing an application server interface, Jane creates a pattern to deploythe PocketBook application 830. At step (2), the cloud applicationplatform queries the security assurance service 810 for a list ofavailable assurance templates. This query includes information about theapplication being deployed (e.g., a “J2EE application with a singlecontext root, built on WebSphere Application Server (WAS) and usingDB2”). Given the specification, the security assurance service 810continues at step (3) to provide templates of type “Internal NetworkSecurity,” “Application Security,” “Data Security” and “IntruderProtection,” along with “high” or “low” security level options for each(see, FIG. 7). The type(s) returned by the security assurance service(and their levels) may vary depending on the application specified, theavailable resources, and the like. At step (4), the cloud applicationplatform displays the simple security templates in a configurator (e.g.,IBM Workload Deployer pattern builder) for easy user selection. At step(5), Jane selects the four templates, e.g., based on her general feelingthat the internal network is secure but frequent attacks and advancedpersistent threats (APTs) are likely from the external network. At step(6), and preferably upon application deployment, the cloud applicationplatform communicates the selected security templates to the cloudservice, preferably along with the details of the application beingdeployed. At step (7), the security assurance service generates a listof configuration steps and presents the list to John for confirmation.The presentment of the list to John (as opposed to Jane, or to someother person) is not a requirement, but it may be a typical use case. Atstep (8), the security assurance service remotely applies theconfiguration changes to create the context-specific secure cloudapplication zone for the to-be-deployed application. At step (9), andthe when the zone creation is completed, the security assurance servicenotifies the cloud application platform (e.g., via a callback) that theconfiguration settings are complete, and that the cloud applicationplatform can continue the deployment process. The deployment iscompleted by the cloud application platform in the usual manner.

Without meant to be limiting, in this particular example scenario(involving the PocketBook application), the security assurance serviceapplies a number of configuration changes, and these were detailedabove. Thus, for example, at sub-step (8.1), the service creates aWebSEAL junction in the Web Security Gateway 816 for the new applicationendpoint. At sub-step (8.2), the service configures the junction and theWAS instance 832 to use basic authentication for internal communication.At sub-step (8.3), the service enables firewalls on the newly-deployedRHEL instances, opening only required endpoint ports. At sub-step (8.4),the services runs AppScan 824 against the newly-deployed application (ina sandbox if needed) and reports back to the user or securityadministrator. At sub-step (8.5), the service provisions a VPN for thenew deployment, e.g., through the PureApplication system 822. Atsub-step (8.6), the service updates Access Manager 812 for authorizedusers to the new application. At sub-step (8.7), the service updates DB2818 and 836 to use an SSL connection from WAS. At sub-step (8.8), theservice configures QRadar 820 log sources from DB2, RHEL instances,WebSEAL and WAS. At step (8.9), the service updates QRadar rules for thenew application. At step (8.10), the system updates IPS 826 rules forthe new application to complete the configuration of thecontext-specific cloud application security zone.

This particular configuration as shown in FIG. 8, as well as theordering of the configuration changes and steps, is merely exemplary. Asa skilled artisan will appreciate, if different security templates areselected, and/or if different resources are available, the nature andsequence of the various configuration changes will of course varyaccordingly.

The following describes representative or additional capabilities of thesecurity assurance service of this disclosure. One or more of theseadditional capabilities may be provided as desired.

The cloud security assurance service may analyze an existing securityenvironment to identify interactions for customized configuration steps,e.g., the service may determine that a virtual private network (VPN) maynot be necessary in a particular configuration because the network isalready isolated by some other device, network or mechanism.

The security assurance service may operate to update configurationsbased on other deployments. Thus, for example, if a web security gatewayis deployed and is already using certificates for other applications,the security assurance service may recognize this and merely upgrade thenewly-deployed application to use certificates as well.

Preferably, security templates available in the system (e.g., in apattern editor) may include wiring and interaction logic. In the contextof an end-user WYSIWYG-type editor, wiring refers to connecting twoelements (e.g., by drawing a line between them), and is a way for an enduser to add a security capability onto his or her application. As seenin FIG. 7, the PocketBook App is wired to the Database. Preferably, thesecurity boxes that show up in the editor have some associated metadata(possibly hidden) that can be used to determine how the boxes interact.As a simple example, if a high-level “Intruder Protection” template hasbeen selected, the metadata may inhibit a lower level template of thistype from being applied. As another more complex example, a securityadministrator may have set a policy that the network must be at least assecure as the application it hosts; then, if the user selects high-leveldata security, the internal network security may be automaticallyupgraded (e.g., in the pattern editor) to high-level. Or, in this lattercircumstance, the system may inhibit the user from attempting to wiretogether a “high application security” box with a “low applicationsecurity” box. Generalizing, and depending on the metadata, the user'sattempts to wire elements thus may be allowed or disallowed.

Thus, and in a typical use scenario of the editor, a first template hasbeen selected. In response to the user selecting a second template andan instruction to wire the second template to the first template,applicable security restrictions with respect to one or both templatesare then enforced.

Preferably, a security administrator interacts with the securityassurance service directly to apply templates to existing deployments,e.g., to upgrade security settings for an application that may have beenattacked.

Preferably, the service enables a security administrator to override aparticular categorization. As a non-limiting example, a highly-securebank network may require a higher level of controls even with respect toan otherwise “low-level” security category.

Preferably, the security assurance services records configurationsettings and can remove security configuration steps when an applicationis removed from the system. This security “removal” function preferablyalso interacts with other systems, e.g., optionally downgrading securitylevels of other applications if their security has been upgraded onlyfor the application being removed.

Preferably, the security administrator is provided the ability to changesecurity templates available in the service, as well as the ability tochange rules around which templates must be used in certaincircumstances.

Preferably, the security assurance service interacts with one or morecloud platforms for management of the virtualized resources. Thus, forexample, the security assurance service may query existing softwarecatalogs in the enterprise to determine security software installed, aswell as their locations and available resources. The service also maytry to auto-discover software in the network, or it may query specificsecurity solutions (such as a log manager) to discover other softwareinstalled in the system.

Preferably, and if resource consumption from high-level security optionsare a concern, the security assurance service can estimate overall costof the selected security template(s) and present this information to theapplication deployer for approval. Or, a security expert optionally mayconfigure “maximum” and “minimum” total security levels allowed andrequired for particular types of applications.

Preferably, a security administrator can use the security assuranceservice to prevent deployment of applications if security templates ofminimum security levels have not been selected.

Preferably, the security assurance service can mine patterns betweenapplication deployments and commonly selected security levels toautomatically suggest security levels for new applications beingdeployed.

Preferably, the security assurance service can interact or interoperatewith security analytics systems or services (e.g., Rational AppScan)during application deployment to gauge overall security level of adeployed application and determine if it fits within an enterprisesecurity policy.

The service also preferably provides for “patching” of securityassurance templates, either manually or automatically (e.g., through anauto-update tool), to improve security recommendations based on selectedtemplates, and to retroactively apply new security configurations toexisting applications.

Preferably, the service can receive reports or other outputs describingcommon vulnerabilities or attack pattern files (e.g. APT patterns) anddetermine if such an attack would be prevented with an existing securityconfiguration. In the event of possible attack exposure, the servicethen generates and optionally applies configuration changes to protectthe environment.

As noted above, preferably the security assurance service operates inconjunction or in association with existing cloud application platforminfrastructure including, without limitation, a cloud applicationplatform with workload deployment functionality. In this manner, thesecurity assurance service supplements or works in across the cloudinfrastructure to facilitate secure context-based applicationdeployment.

In the example scenario in FIG. 8, the security templates and theirassociated security configuration changes are implemented during theapplication deployment process. In that example, the applicationdeployment is initiated, then the security configuration changes arecarried out, after which the remainder of the application deploymentprocess contemplates. While this is a typical operating scenario, thesecurity configuration changes may be implemented orthogonally to theactual deployment itself. Thus, for example, the security configurationchanges may be implemented in an off-line process before the actualapplication deployment is initiated. In the alternative, the applicationdeployment may be in initiated and completed, and then followed by aseparate execution thread of the security assurance service. Thus, agiven context-based cloud application security zone may be createdbefore, during or after actual application deployment.

The tooling required for implementing the security configuration changesfor one or more particular security resources (as identified by aparticular security template) may be specified or controlled by thetemplate directly, or indirectly.

As described above, permitted administrators may have the ability toupdate templates directly. More commonly, it may be desirable to definesecurity policies separate from the templates. For example, a “low” datasecurity template may only require SSL, but an administrator may haveconfigured the assurance service (as a matter of policy) to require,say, disk encryption for all deployments regardless of chosen templates.Functionally, this is equivalent to administrators updating thetemplates as described. Thus, in an alternative embodiment, suchadministrator changes are stored as policies separate from thetemplates. Then, to determine how to create the security zone, thesystem checks the available software and references with templaterequirements, as well as such administrator settings. Such policies maybe system-wide, or they be scoped to certain domains, e.g., allworkloads running on a certain cloud, or all workloads built on certainsoftware, or the like.

The above-described subject matter provides many advantages. Inparticular, the above-described and illustrated techniques of thisdisclosure provide for a cross-system, template-based approach to usecategorization of applications and deployment technologies to securelyprovision applications into an environment, updating all or relevantsecurity infrastructure (e.g., firewalls, event loggers, directories,reverse proxies, and so forth) with the security settings necessaryand/or appropriate to that application and deployment topology. Thistemplate-based approach preferably relies on abstract or “generalized”categories, with the service then automatically providing the advancedprovisioning in the form of the necessary configuration changes “underthe covers.”

The approach herein provides a centralized or federated securityassurance service that manages and provisions hardware, software,network, and cloud resources as needed for application security. Thetechniques described take advantage of abstract assurance securitytemplates to augment application development. The templates preferablyare context-based that are derived from information on availableresources and desired security goals. A list of security templates maybe easily customized based on availability of security software in theenvironment, and/or combined with properties of the application andmiddleware. The service also interprets abstract merged templates togenerate specific configuration steps. The service analyzes existingsecurity and cloud environments to identify interactions for customizedconfiguration steps. The service generates an end-to-endsoftware-defined security environment for newly-deployed applications.The service upgrades security for other applications if impacted by asecurity requirement of the new application. The service enablesautomatic creation of security solutions as needed for applicationsecurity requirements, such as creation of a VPN or DMZ, or addition offirewalls. The described approach enables distillation of a list ofpending security configuration changes that a security expert wouldunderstand, and also provides for optional confirmation and approval ofsuch changes. The template approach also easily integrates with othercloud deployment tools, such as application pattern tools.

The assurance service can be queried with details of the application tobe deployed to determine available security measures appropriate forthat application. The assurance service preferably is centrally-managedto provide a higher or lower level of security assurance. The approachenables a security environment to be de-configured when an applicationis un-deployed. The service also enables lowering of security levels forimpacted applications when a higher-security level application isde-configured. The service also enables real-time interaction managementof related assurance templates to provide user interface (UI)capabilities, such as wiring, or mutually-exclusive templates (e.g.,addition of SSL may affect key length for different assurance levels).The service provides for auto-discovery or integration with a softwarerepository to identify available security software and licensedresources for selection of available assurance templates. Preferably,the service provides for administrative capability to override appliedsecurity templates, on a per-application basis. The approach enablesestimation of system-wide costs of security configuration changes, aswell as presenting those costs to the user in an easy-to-understandformat. The service also enables templates to be set around the cost ofsecurity settings, e.g., setting a maximum level to the securityenvironment cost, in which case the end user can the select only asubset of security assurance capabilities. The approach enables the userto establish a centralized security policy to prevent deployment ofapplications if security templates of minimum security levels have notbeen selected.

The service provides for analytics that can be used to suggest securitytemplates, e.g., based on templates used in the past. The use ofsecurity analytics during application deployment provides a useful wayto determine if the application deployment fits within the enterprise'ssecurity policy.

The service also provides for retroactive application of upgradedsecurity templates to existing applications. The service also enablesintegration with systems that perform security scans or output securityintelligence reports to facilitate identification of gaps in systemprotection, and to recommend and optionally automatically apply missingconfigurations or products.

As described, the approach herein may be implemented manually or in anautomated manner, in whole or in part.

While a preferred operating environment and use case (a cloud deploymentappliance or platform) has been described, the techniques herein may beused in any other operating environment in which it is desired to deployapplications or other services while enforcing a given security context.

As has been described, the functionality described above may beimplemented as a standalone approach, e.g., one or more software-basedfunctions executed by one or more hardware processors, or it may beavailable as a managed service (including as a web service via aSOAP/XML interface). The particular hardware and software implementationdetails described herein are merely for illustrative purposes are notmeant to limit the scope of the described subject matter.

More generally, computing devices within the context of the disclosedsubject matter are each a data processing system (such as shown in FIG.2) comprising hardware and software, and these entities communicate withone another over a network, such as the Internet, an intranet, anextranet, a private network, or any other communications medium or link.The applications on the data processing system provide native supportfor Web and other known services and protocols including, withoutlimitation, support for HTTP, FTP, SMTP, SOAP, XML, WSDL, UDDI, andWSFL, among others. Information regarding SOAP, WSDL, UDDI and WSFL isavailable from the World Wide Web Consortium (W3C), which is responsiblefor developing and maintaining these standards; further informationregarding HTTP, FTP, SMTP and XML is available from Internet EngineeringTask Force (IETF).

In addition to the cloud-based environment, the techniques describedherein may be implemented in or in conjunction with various server-sidearchitectures including simple n-tier architectures, web portals,federated systems, and the like.

Still more generally, the subject matter described herein can take theform of an entirely hardware embodiment, an entirely software embodimentor an embodiment containing both hardware and software elements. In apreferred embodiment, the security assurance service (or any componentthereof) is implemented in software, which includes but is not limitedto firmware, resident software, microcode, and the like. Furthermore,the download and delete interfaces and functionality can take the formof a computer program product accessible from a computer-usable orcomputer-readable medium providing program code for use by or inconnection with a computer or any instruction execution system. For thepurposes of this description, a computer-usable or computer readablemedium can be any apparatus that can contain or store the program foruse by or in connection with the instruction execution system,apparatus, or device. The medium can be an electronic, magnetic,optical, electromagnetic, infrared, or a semiconductor system (orapparatus or device). Examples of a computer-readable medium include asemiconductor or solid state memory, magnetic tape, a removable computerdiskette, a random access memory (RAM), a read-only memory (ROM), arigid magnetic disk and an optical disk. Current examples of opticaldisks include compact disk-read only memory (CD-ROM), compactdisk-read/write (CD-R/W) and DVD. The computer-readable medium is atangible, non-transitory item.

The computer program product may be a product having programinstructions (or program code) to implement one or more of the describedfunctions. Those instructions or code may be stored in a computerreadable storage medium in a data processing system after beingdownloaded over a network from a remote data processing system. Or,those instructions or code may be stored in a computer readable storagemedium in a server data processing system and adapted to be downloadedover a network to a remote data processing system for use in a computerreadable storage medium within the remote system.

In a representative embodiment, the techniques are implemented in aspecial purpose computing platform, preferably in software executed byone or more processors. The software is maintained in one or more datastores or memories associated with the one or more processors, and thesoftware may be implemented as one or more computer programs.Collectively, this special-purpose hardware and software comprises thefunctionality described above.

In the preferred embodiment as described above, the functionalityprovided herein is implemented as an adjunct or extension to an existingcloud compute deployment management solution.

While the above describes a particular order of operations performed bycertain embodiments of the invention, it should be understood that suchorder is exemplary, as alternative embodiments may perform theoperations in a different order, combine certain operations, overlapcertain operations, or the like. References in the specification to agiven embodiment indicate that the embodiment described may include aparticular feature, structure, or characteristic, but every embodimentmay not necessarily include the particular feature, structure, orcharacteristic.

Finally, while given components of the system have been describedseparately, one of ordinary skill will appreciate that some of thefunctions may be combined or shared in given instructions, programsequences, code portions, and the like.

The techniques herein provide for improvements to a technology ortechnical field, namely, computing entities that manage clouddeployments, as well as improvements to the functioning of theapplication deployment mechanism itself, namely, by extending itsconventional functionality to be security-context aware based oneasy-to-understand templates having associated instructions for securityconfiguration tooling changes).

The particular nomenclature of a “template” as used herein should not bedeemed limited to any particular format or structure, as the notion isintended to refer to any construct (irrespective of structure or form)that includes the type of information identified (the pre-configuredsecurity requirements associated with a particular security assurancelevel), that preferably is specified with a simple-to-understandreference (e.g., “high security”), and that is adapted to be translatedby the service/system (typically along with the system configuration,etc.) into the granular requirements necessary to implement that levelof specified security. Depending on implementation, a “template” maycomprise a set of configuration data having these properties andcharacteristics.

Having described our invention, what we now claim is as follows:
 1. Amethod for improving a cloud application deployment service operative ina cloud application environment, comprising: receiving information on aset of security capabilities available in the cloud applicationenvironment to define a security context, the security capabilitiesincluding identification of at least one security product or its currentsecurity settings; receiving a selection of a security assurance level,wherein the security assurance level is specified in a template by a setof general security requirements, at least one of the set of generalsecurity requirements being specified in a manner that does not exposeat least some specific security resource requirements necessary toimplement the security assurance level, the template including aninterface to enable receipt of an instruction to wire a securitycapability into an application being deployed by the cloud applicationdeployment service; for a given security assurance level, mapping the atleast one of the set of general security requirements being specified tothe identification of the at least one security product or its currentsecurity settings; and responsive to receipt of the selection of thesecurity assurance level that includes the mapping, and based at leastin part on the security context, applying, via automation, configurationchanges to a set of security resources in the cloud applicationenvironment to provide a context-based security assurance zone for theapplication being deployed by the cloud application deployment service,the configuration changes installing the at least one security productor adjusting its current security settings, and enforcing a wiringinstruction as specified in the template, wherein enforcing the wiringinstruction enforces a wiring restriction between a first securityresource and a second security resource in response to receipt of aninstruction to wire the security capability; wherein the receiving andconfiguring steps are carried out in software executing in a hardwareelement.
 2. The method as described in claim 1 further includingproviding a set of templates, each template having associated therewithone of the security assurance levels, and wherein the selection of thesecurity assurance level corresponds to selection of a template.
 3. Themethod as described in claim 2 wherein the set of templates are providedto an end user via user interface tooling associated with the cloudapplication environment, wherein receipt of the selection corresponds toa selection by the end user via the user interface tooling.
 4. Themethod as described in claim 2 wherein the templates are provided to asecurity administrator via an administrative interface.
 5. The method asdescribed in claim 4 further including adjusting the set of securityrequirements associated with a template via the administrativeinterface.
 6. The method as described in claim 1 wherein the methodfurther includes adjusting the set of security resources configured. 7.The method as described in claim 6 wherein the adjusting occurs upon oneof: de-configuration of a security environment when an application isun-deployed, modification of a security environment for a firstapplication when a second application is deployed, and modification of asecurity environment for a first application when a second applicationhaving a higher security level than that of the first application isde-configured.
 8. Apparatus, comprising: a processor; computer memoryholding computer program instructions executed by the processor toimprove a cloud application deployment service operative in a cloudapplication environment, the computer program instructions comprising:program code, operative to receive information on a set of securitycapabilities available in the cloud application environment, to define asecurity context, the security capabilities including identification ofat least one security product or its current security settings; programcode, operative to receive a selection of a security assurance level,wherein the security assurance level is specified in a template by a setof general security requirements, at least one of the set of generalsecurity requirements being specified in a manner that does not exposeat least some specific security resource requirements necessary toimplement the security assurance level, the template including aninterface to enable receipt of an instruction to wire a securitycapability into an application being deployed by the cloud applicationdeployment service; program code, operative for a given securityassurance level, to map the at least one of the set of general securityrequirements being specified to the identification of the at least onesecurity product or its current security settings; and program code,responsive to receipt of the selection of the security assurance levelthat includes the mapping, and based at least in part on the securitycontext, to apply, via automation, configuration changes to a set ofsecurity resources in the cloud application environment to provide acontext-based security assurance zone for the application being deployedby the cloud application deployment service, the configuration changesinstalling the at least one security product or adjusting its currentsecurity settings, and enforcing any a wiring instruction as specifiedin the template, wherein enforcing the wiring instruction enforces awiring restriction between a first security resource and a secondsecurity resource in response to receipt of an instruction to wire thesecurity capability.
 9. The apparatus as described in claim 8 whereinthe computer program instructions further include program code toprovide a set of templates, each template having associated therewithone of the security assurance levels, and wherein the selection of thesecurity assurance level corresponds to selection of a template.
 10. Theapparatus as described in claim 9 wherein the set of templates areprovided to an end user via user interface tooling associated with thecloud application environment, wherein receipt of the selectioncorresponds to a selection by the end user via the user interfacetooling.
 11. The apparatus as described in claim 9 further including anadministrative interface, and wherein the templates are provided to asecurity administrator via the administrative interface.
 12. Theapparatus as described in claim 11 wherein the computer programinstructions further include program code to adjust the set of securityrequirements associated with a template via the administrativeinterface.
 13. The apparatus as described in claim 8 further includingprogram code operative to adjust the set of security resourcesconfigured.
 14. The apparatus as described in claim 13 wherein theadjusting occurs upon one of: de-configuration of a security environmentwhen an application is un-deployed, modification of a securityenvironment for a first application when a second application isdeployed, and modification of a security environment for a firstapplication when a second application having a higher security levelthan that of the first application is de-configured.
 15. A computerprogram product in a non-transitory computer readable medium for use ina data processing system, the computer program product holding computerprogram instructions executed by the data processing system to improve acloud application deployment service operative in a cloud applicationenvironment, the computer program instructions comprising: program code,operative to receive information on a set of security capabilitiesavailable in the cloud application environment, to define a securitycontext, the security capabilities including identification of at leastone security product or its current security settings; program code,operative to receive a selection of a security assurance level, whereinthe security assurance level is specified in a template by a set ofgeneral security requirements, at least one of the set of generalsecurity requirements being specified in a manner that does not exposeat least some specific security resource requirements necessary toimplement the security assurance level, the template including aninterface to enable receipt of an instruction to wire a securitycapability into an application being deployed by the cloud applicationdeployment service; program code, operative for a given securityassurance level, to map the at least one of the set of general securityrequirements being specified to the identification of the at least onesecurity product or its current security settings; and program code,responsive to receipt of the selection of the security assurance levelthat includes the mapping, and based at least in part on the securitycontext, to apply, via automation, configuration changes to a set ofsecurity resources in the cloud application environment to provide acontext-based security assurance zone for the application being deployedby the cloud application deployment service, the configuration changesinstalling the at least one security product or adjusting its currentsecurity settings, and enforcing a wiring instruction as specified inthe template, wherein enforcing the wiring instruction enforces a wiringrestriction between a first security resource and a second securityresource in response to receipt of an instruction to wire the securitycapability.
 16. The computer program product as described in claim 15wherein the computer program instructions further include program codeto provide a set of templates, each template having associated therewithone of the security assurance levels, and wherein the selection of thesecurity assurance level corresponds to selection of a template.
 17. Thecomputer program product as described in claim 16 wherein the set oftemplates are provided to an end user via user interface toolingassociated with the cloud application environment, wherein receipt ofthe selection corresponds to a selection by the end user via the userinterface tooling.
 18. The computer program product as described inclaim 16 further including an administrative interface, and wherein thetemplates are provided to a security administrator via theadministrative interface.
 19. The computer program product as describedin claim 18 wherein the computer program instructions further includeprogram code to adjust the set of security requirements associated witha template via the administrative interface.
 20. The computer programproduct as described in claim 15 further including program codeoperative to adjust the set of security resources configured.
 21. Thecomputer program product as described in claim 20 wherein the adjustingoccurs upon one of: de-configuration of a security environment when anapplication is un-deployed, modification of a security environment for afirst application when a second application is deployed, andmodification of a security environment for a first application when asecond application having a higher security level than that of the firstapplication is de-configured.